fix(ci): publish to JSR (Deno project), not npm — repair broken publish#39
Merged
Conversation
preference-injector is Deno + ReScript (deno.json, JSR name, NO package.json), but publish.yml ran 'npm ci / npm publish' — which can never work without a package.json (this is why the failure only ever surfaced at release time). The correct registry is JSR. Switches publish.yml to setup-deno -> deno task build -> deno publish, with id-token: write so JSR records build provenance natively. Adds the required 'exports' to deno.json (was missing, so JSR couldn't resolve the entry). NOTE: first release will validate the build chain — 'deno task build' runs 'rescript build', which needs the ReScript toolchain available in CI; if that toolchain isn't wired (no package.json to install rescript from), that's a pre-existing build gap to close separately. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the 'how did it just surface' repo. preference-injector is Deno+ReScript (
deno.json, JSR name@hyperpolymath/preference-injector, nopackage.json), butpublish.ymlrannpm ci/npm publish— impossible without a package.json. Because the publish job only runs on release, it silently failed only at release time, so it stayed invisible until the provenance audit was the first thing to actually read it.Fix: switch to JSR (the correct registry) —
setup-deno→deno task build→deno publish, withid-token: writeso JSR records build provenance natively. Adds the missingexportstodeno.json.deno task buildrunsrescript build— if the ReScript toolchain isn't available in CI (no package.json to install it from), that's a pre-existing build gap to close separately. Also note the repo is mid ReScript→AffineScript migration. 🤖 Generated with Claude Code